v26.41.0 release notes - #38667
Merged
Merged
Conversation
Adds the v26.41.0 section to the releases index and the corresponding self-managed operator compatibility row. Dates are provisional and will be set for real by the final snapshot.
Adds the rc.2 increment to the v26.41.0 section: MySQL primary-key snapshot parallelism is now on by default (#38656). Provisional dates are unchanged from rc.1 (Cloud 2026-09-10, Self-Managed 2026-09-11), so the operator-compatibility row needs no update this snapshot.
Adds the rc.3 increment to the v26.41.0 section: the Self-Managed Console cluster list now shows the per-replica usage table (#38650). Provisional dates are unchanged from rc.1 (Cloud 2026-09-10, Self-Managed 2026-09-11), so the operator-compatibility row needs no update this snapshot.
Adds the rc.4 increment to the v26.41.0 section: an `ALTER MATERIALIZED VIEW ... APPLY REPLACEMENT` applied during a zero-downtime upgrade could leave the upgraded environment on the view's previous definition (#38677). This is distinct from the rc.1 bullet for #38545, which covered the single-process case; #38677 fixes the 0dt case that reproduces even between two versions carrying #38545. Provisional dates are unchanged from rc.1 (Cloud 2026-09-10, Self-Managed 2026-09-11), so the operator-compatibility row needs no update this snapshot.
maheshwarip
pushed a commit
that referenced
this pull request
Sep 8, 2026
Release notes for `v26.40.2`, a patch release. One commit is added per snapshot; this train has no RC snapshots, so the single `final` commit carries the whole note with the real release dates. Snapshot drafts (with PR links) in mz-skills: - final: [release_notes.md](https://github.com/MaterializeInc/mz-skills/blob/main/data/mz-release-notes/v26.40.2/final/release_notes.md) / [omitted.md](https://github.com/MaterializeInc/mz-skills/blob/main/data/mz-release-notes/v26.40.2/final/omitted.md) **Borderline PRs omitted:** final: 1 — [omitted.md#borderline](https://github.com/MaterializeInc/mz-skills/blob/main/data/mz-release-notes/v26.40.2/final/omitted.md#borderline) ### Two things for the reviewer - **Release dates are inferred, not supplied.** Cloud 2026-09-07 / Self-Managed 2026-09-08, derived from the `v26.40.2` tag's commit date (2026-09-07T19:27:35Z) plus one day. The tag was cut Monday evening UTC, so a next-day Cloud rollout is at least as likely as a same-day one. Please confirm both dates before merging. - **This section is the same increment as `v26.41.0-rc.4`.** Both trains took the same two `release-blocker` cherry-picks on 2026-09-07, so `#38677` is drafted as a Bug Fix in both #38667 and here. `v26.40.2` ships it to Cloud first, so if both merge as drafted the same fix is announced in consecutive releases. `v26.40.1` (#38675) raised the same question and answered it the other way. Worth settling once for both patches. Merge ordering: `## v26.40.2` must sit above `## v26.40.1` (#38675), which must sit above `## v26.40.0`. #38675, #38667, and #38365 (v26.38.1) are all still open, so whichever merges last will need its section placed by hand relative to the others. Co-authored-by: Claude <noreply@anthropic.com>
maheshwarip
approved these changes
Sep 11, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Dates in RC snapshots are provisional until the release ships. One commit is added per snapshot; the final snapshot sets the real dates.
Snapshot drafts (with PR links) in mz-skills:
Borderline PRs omitted: rc.1: 13 — review borderline calls, rc.2: 0, rc.3: 0, rc.4: 1 — review borderline calls